Hey @Codencode, I am thinking about this and I am not sure if it's the correct way to handle this.

I think that native modules that are on the disk should be updated, because they could break the module page after the upgrade. Many modules are instantiated on the module page - even if not installed.

Hey @Codencode, I am thinking about this and I am not sure if it's the correct way to handle this.

I think that native modules that are on the disk should be updated, because they could break the module page after the upgrade. Many modules are instantiated on the module page - even if not installed.

Hi @Hlavtox,

The check I implemented is meant to prevent the module from being updated at the database level, meaning that the scripts in the module's upgrade folder are not executed.

In practice, the module is still downloaded, and the files are updated, but if the module is not actually installed, the database update is not performed.
I believe this behavior is correct: it wouldn’t make sense to execute database operations for a module that is not truly installed.

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

The issue has been resolved in the "dev" version, so it should no longer exist in the next release.